Limit monitor-specific scaling to supported autoscale modes #3475
+29
−1
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
These changes have following affects:
Testing
Scenario#1: Starting application with
-Dswt.autoScale=int200Result: App should start (if monitor-specific scaling is not checked in Appearance page), but option to turn on monitor-specific scaling in Appearance page should be disabled.
Scenario#2: Starting application with
-Dswt.autoScale=int200and-Dswt.autoScale.updateOnRuntime=trueResult: App will start, user will see an error dialog stating the incompatibility of an option and monitor specific-scaling will be disabled.
Scenario#3: Starting application with
-Dswt.autoScale=int200and-Dswt.autoScale.updateOnRuntime=trueand
-Dswt.autoScale.force=trueResult: makes more sense with swt applications. if user really wants to use other scaling mode with monitor-specific scaling.
Scenario#4: Starting application with
-Dswt.autoScale=quarterResult: App should start, and user should be able to turn on/off the monitor-specific scaling in Appearance page.
Note: following is the list of allowed autoscale values to be paired with monitor-specific scaling: ["false", "quarter", "exact"]
Dependency